Reporting power headroom

ABSTRACT

Apparatuses, methods, and systems are disclosed for reporting power headroom. One apparatus includes a processor that identifies a transmission occasion for AUL transmission on an unlicensed serving cell and generates a PHR MAC CE. The apparatus includes a transceiver that transmits the PHR MAC CE with an AUL transmission to a RAN node in the mobile communication network, wherein transmitting the PHR MAC CE includes indicating timing information corresponding to the PHR.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to reporting powerheadroom.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), Fifth Generation Core Network (“5CG”),Fifth Generation System (“5GS”), Authentication, Authorization andAccounting (“AAA”), Access and Mobility Management Function (“AMF”),Access to Restricted Local Operator Services (“ARLOS”),Positive-Acknowledgment (“ACK”), Application Programming Interface(“API”), Authentication Center (“AuC”), Access Stratum (“AS”),Autonomous Uplink (“AUL”), AUL Downlink Feedback Information(“AUL-DFI”), Base Station (“BS”), Binary Phase Shift Keying (“BPSK”),Bandwidth Part (“BWP”), Clear Channel Assessment (“CCA”), ControlElement (“CE”), Cyclic Prefix (“CP”), Cyclical Redundancy Check (“CRC”),Channel State Information (“CSI”), Common Search Space (“CSS”),Connection Mode (“CM”, this is a NAS state in 5GS), Core Network (“CN”),Control Plane (“CP”), Data Radio Bearer (“DRB”), Discrete FourierTransform Spread (“DFTS”), Downlink Control Information (“DCI”),Downlink (“DL”), Downlink Pilot Time Slot (“DwPTS”), Dual Connectivity(“DC”), Dual Registration mode (“DR mode”), Enhanced Clear ChannelAssessment (“eCCA”), Enhanced Licensed Assisted Access (“eLAA”),Enhanced Mobile Broadband (“eMBB”), Evolved Node-B (“eNB”), EvolvedPacket Core (“EPC”), Evolved Packet System (“EPS”), EPS MobilityManagement (“EMM”, this is a NAS state in EPS), Evolved UMTS TerrestrialRadio Access (“E-UTRA”), Evolved UMTS Terrestrial Radio Access Network(“E-UTRAN”), European Telecommunications Standards Institute (“ETSI”),Frame Based Equipment (“FBE”), Frequency Division Duplex (“FDD”),Frequency Division Multiple Access (“FDMA”), Frequency DivisionOrthogonal Cover Code (“FD-OCC”), General Packet Radio Service (“GPRS”),Generic Public Service Identifier (“GPSI”), Guard Period (“GP”), GlobalSystem for Mobile Communications (“GSM”), Globally Unique Temporary UEIdentifier (“GUTI”), Hybrid Automatic Repeat Request (“HARQ”), HomeSubscriber Server (“HSS”), Home Public Land Mobile Network (“HPLMN”),Information Element (“IE”), Internet-of-Things (“IoT”), InternationalMobile Subscriber Identity (“IMSI”), Licensed Assisted Access (“LAA”),Load Based Equipment (“LBE”), Listen-Before-Talk (“LBT”), Long TermEvolution (“LTE”), Multiple Access (“MA”), Mobility Management (“MM”),Mobility Management Entity (“MME”), Modulation Coding Scheme (“MCS”),Machine Type Communication (“MTC”), Multiple Input Multiple Output(“MIMO”), Mobile Station International Subscriber Directory Number(“MSISDN”), Multi User Shared Access (“MUSA”), Narrowband (“NB”),Negative-Acknowledgment (“NACK”) or (“NAK”), New Generation (5G) Node-B(“gNB”), New Generation Radio Access Network (“NG-RAN”, a RAN used for5GS networks), New Radio (“NR”, a 5G radio access technology; alsoreferred to as “5G NR”), Non-Access Stratum (“NAS”), Network ExposureFunction (“NEF”), Non-Orthogonal Multiple Access (“NOMA”), Network SliceSelection Assistance Information (“NSSAI”), Operation and MaintenanceSystem (“OAM”), Orthogonal Frequency Division Multiplexing (“OFDM”),Packet Data Unit (“PDU”, used in connection with ‘PDU Session’), PacketSwitched (“PS”, e.g., Packet Switched domain or Packet Switchedservice), Primary Cell (“PCell”), Physical Broadcast Channel (“PBCH”),Physical Downlink Control Channel (“PDCCH”), Physical Downlink SharedChannel (“PDSCH”), Pattern Division Multiple Access (“PDMA”), PhysicalHybrid ARQ Indicator Channel (“PHICH”), Physical Random Access Channel(“PRACH”), Physical Resource Block (“PRB”), Physical Uplink ControlChannel (“PUCCH”), Physical Uplink Shared Channel (“PUSCH”), Public LandMobile Network (“PLMN”), Quality of Service (“QoS”), Quadrature PhaseShift Keying (“QPSK”), Radio Access Network (“RAN”), Radio AccessTechnology (“RAT”), Radio Resource Control (“RRC”), Random-AccessChannel (“RACH”), Random Access Response (“RAR”), Radio NetworkTemporary Identifier (“RNTI”), Reference Signal (“RS”), RegistrationArea (“RA”, similar to tacking area list used in LTE/EPC), RegistrationManagement (“RM”, refers to NAS layer procedures and states), RemainingMinimum System Information (“RMSI”), Resource Spread Multiple Access(“RSMA”), Round Trip Time (“RTT”), Receive (“RX”), Radio Link Control(“RLC”), Sparse Code Multiple Access (“SCMA”), Scheduling Request(“SR”), Single Carrier Frequency Division Multiple Access (“SC-FDMA”),Secondary Cell (“SCell”), Shared Channel (“SCH”), Session Management(“SM”), Session Management Function (“SMF”), Service Provider (“SP”),Signal-to-Interference-Plus-Noise Ratio (“SINR”), Single Network SliceSelection Assistance Information (“S-NSSAI”), Single Registration mode(“SR mode”), Sounding Reference Signal (“SRS”), System Information Block(“SIB”), Synchronization Signal (“SS”), Supplementary Uplink (“SUL”),Subscriber Identification Module (“SIM”), Tracking Area (“TA”),Transport Block (“TB”), Transport Block Size (“TBS”), Time-DivisionDuplex (“TDD”), Time Division Multiplex (“TDM”), Time DivisionOrthogonal Cover Code (“TD-OCC”), Transmission Time Interval (“TTI”),Transmit (“TX”), Unified Access Control (“UAC”), Unified Data Management(“UDM”), User Data Repository (“UDR”), Uplink Control Information(“UCI”), User Entity/Equipment (Mobile Terminal) (“UE”), UEConfiguration Update (“UCU”), UE Route Selection Policy (“URSP”), Uplink(“UL”), User Plane (“UP”), Universal Mobile Telecommunications System(“UMTS”), UMTS Subscriber Identification Module (“USIM”), UMTSTerrestrial Radio Access (“UTRA”), UMTS Terrestrial Radio Access Network(“UTRAN”), Uplink Pilot Time Slot (“UpPTS”), Ultra-reliability andLow-latency Communications (“URLLC”), Visited Public Land Mobile Network(“VPLMN”), and Worldwide Interoperability for Microwave Access(“WiMAX”). As used herein, “HARQ-ACK” may represent collectively thePositive Acknowledge (“ACK”) and the Negative Acknowledge (“NACK”). ACKmeans that a TB is correctly received while NACK (or NAK) means a TB iserroneously received.

For LTE eLAA, autonomous uplink (AUL) transmissions can be enabledthrough a combination of RRC signaling and an activation messageconveyed by a DCI in a physical control channel. The RRC configurationincludes subframes in which the UE is allowed to transmit autonomously,as well as eligible HARQ process IDs. The activation message includesthe resource block assignment (RBA) and MCS, from which the UE is ableto determine the transport block size for any AUL transmission.

When autonomous uplink (AUL) for unlicensed access in NR (NR-U) is used,the gNB may be unable to determine when an UL transmission/TB wasinitially generated due to potential LBT failures, even if the following(re)transmission of the same HARQ process are correctly decoded by thegNB. Such uncertainty may have in particular for PHR transmissions somenegative impact, because the PHR content at the time of the transmissionmay not really reflect the status when it was generated.

BRIEF SUMMARY

Disclosed are procedures for reporting power headroom. Apparatuses andsystems also perform the functions of the methods. The methods may alsobe embodied in one or more computer program products comprising acomputer readable storage medium that stores executable code that, whenexecuted by a processor, perform the steps of the methods.

One method of a UE for reporting power headroom includes identifying atransmission occasion for AUL transmission on an unlicensed servingcell. The method includes generating a power headroom report (“PHR”)Medium Access Control (“MAC”) Control Element (“CE”)and transmitting thePHR MAC CE with an AUL transmission to a RAN node in the mobilecommunication network, wherein transmitting the PHR MAC CE includestiming information corresponding to the PHR.

Another method of a UE for reporting power headroom includes identifyinga first transmission occasion for AUL transmission on an unlicensedserving cell and generating a PHR MAC CE including power headroominformation for each activated serving cell configured with uplink,wherein the power headroom information for an activated serving cell iscalculated for a predetermined PHR type in response to the serving cellbeing configured with two UL carriers. The method includes transmittingthe PHR MAC CE in an AUL transmission to a RAN node in the mobilecommunication network.

Yet another method of a UE for reporting power headroom includesidentifying a first transmission occasion on a configured uplink grantresource. The method includes generating a PHR MAC CE including powerheadroom information for each activated serving cell and transmittingthe PHR MAC CE to a RAN node in the mobile communication network. Here,the power headroom information is calculated for a predetermined PHRtype in response to a serving cell being configured with two ULcarriers.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for reporting power headroom;

FIG. 2 is a diagram illustrating one embodiment of uplink controlinformation for autonomous uplink transmission;

FIG. 3 is a diagram illustrating one embodiment of a MAC control elementfor power headroom reporting;

FIG. 4 is a schematic block diagram illustrating one embodiment of auser equipment apparatus that may be used for reporting power headroom;

FIG. 5 is a schematic block diagram illustrating one embodiment of abase station apparatus that may be used for reporting power headroom;

FIG. 6 is a block diagram illustrating one embodiment of a method forreporting power headroom;

FIG. 7 is a block diagram illustrating another embodiment of a methodfor reporting power headroom; and

FIG. 8 is a block diagram illustrating a further embodiment of a methodfor reporting power headroom.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects.

For example, the disclosed embodiments may be implemented as a hardwarecircuit comprising custom very-large-scale integration (“VLSI”) circuitsor gate arrays, off-the-shelf semiconductors such as logic chips,transistors, or other discrete components. The disclosed embodiments mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices, or the like. As another example, the disclosed embodiments mayinclude one or more physical or logical blocks of executable code whichmay, for instance, be organized as an object, procedure, or function.

Furthermore, embodiments may take the form of a program product embodiedin one or more computer readable storage devices storing machinereadable code, computer readable code, and/or program code, referredhereafter as code. The storage devices may be tangible, non-transitory,and/or non-transmission. The storage devices may not embody signals. Ina certain embodiment, the storage devices only employ signals foraccessing code.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random-access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object-oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

As used herein, a list with a conjunction of “and/or” includes anysingle item in the list or a combination of items in the list. Forexample, a list of A, B and/or C includes only A, only B, only C, acombination of A and B, a combination of B and C, a combination of A andC or a combination of A, B and C. As used herein, a list using theterminology “one or more of” includes any single item in the list or acombination of items in the list. For example, one or more of A, B and Cincludes only A, only B, only C, a combination of A and B, a combinationof B and C, a combination of A and C or a combination of A, B and C. Asused herein, a list using the terminology “one of includes one and onlyone of any single item in the list. For example, “one of A, B and C”includes only A, only B or only C and excludes combinations of A, B andC. As used herein, “a member selected from the group consisting of A, B,and C,” includes one and only one of A, B, or C, and excludescombinations of A, B, and C.” As used herein, “a member selected fromthe group consisting of A, B, and C and combinations thereof” includesonly A, only B, only C, a combination of A and B, a combination of B andC, a combination of A and C or a combination of A, B and C.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. This code may be provided to a processor of ageneral-purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart diagramsand/or block diagrams.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the flowchartdiagrams and/or block diagrams.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart diagrams and/or block diagrams.

The flowchart diagrams and/or block diagrams in the Figures illustratethe architecture, functionality, and operation of possibleimplementations of apparatuses, systems, methods, and program productsaccording to various embodiments. In this regard, each block in theflowchart diagrams and/or block diagrams may represent a module,segment, or portion of code, which includes one or more executableinstructions of the code for implementing the specified logicalfunction(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

Invention Overview

Generally, the present disclosure describes systems, methods, andapparatus for reporting power headroom. In certain wirelesscommunications networks, such as LTE eLAA, autonomous uplink (“AUL”)transmissions are enabled through a combination of RRC signaling and anactivation message conveyed by a DCI in a physical control channel. TheRRC configuration includes subframes in which the UE is allowed totransmit autonomously, as well as eligible HARQ process IDs. Theactivation message includes the resource block assignment (“RBA”) and amodulation and coding scheme (“MCS”), from which the UE is able todetermine the transport block size for any AUL transmission.

It is possible to autonomously retransmit data pertaining to a transportblock that has not been received correctly by the eNB. For this purpose,the UE monitors AUL downlink feedback information (e.g., “AUL-DIP”),transmitted by the eNB. The AUL-DFI includes HARQ-ACK information forthe AUL-enabled HARQ process IDs. In case the UE detects a NACK message,it may try to autonomously access the channel for a retransmission ofthe same transport block in the corresponding HARQ process. As asafe-guard against errors, an AUL transmission includes at least theHARQ process ID and a new data indicator (“NDI”) accompanying the PUSCH.In various embodiments, the AUL transmission includes uplink controlinformation, AUL-UCI, which contains the HARQ process ID and NDI.

It is also possible for the eNB to transmit an uplink grant through aDCI that assigns uplink resources for a retransmission of the sametransport block using the indicated HARQ process. It is further possiblethat the eNB transmits an uplink grant through a DCI that assigns uplinkresources for a transmission of a new transport block using theindicated HARQ process. In other words, even though a HARQ process IDmay be eligible for AUL transmissions, the eNB still has access to thisprocess at any time through a scheduling grant (e.g., in DCI).Conventionally, if the UE detects a grant for an UL transmission for asubframe that is eligible for AUL (according to the RRC configuration),it will follow the received grant and will not perform an AULtransmission in that subframe.

When AUL for unlicensed access in NR (referred to as AUL for NR-U) isused, the gNB may be unable to determine when an UL transmission/TB wasinitially generated due to potential listen-before-talk (“LBT”)failures, even if the following (re)transmission of the same HARQprocess are correctly decoded by the gNB. For PHR transmissions, inparticular, such uncertainty may have some negative impact, because thePHR content at the time of the transmission may not accurately reflectthe status when it was generated. That could affect UL scheduling andlink adaptation.

A more serious problem is that for the SUL case, e.g., UE is configuredwith two UL carriers for a serving cell, gNB needs to know when PHR wasgenerated in order to know what PHR type is reported in the PHR MAC CE,e.g., type-1 or type-3 PHR. Currently, the UE is to report either type-1or type-3 PH depending on whether UE determined a real or virtual PH forthe two carriers.

If a UE is configured with two UL carriers for a serving cell and if theUE reports a UE capability “simultaneousTxSUL-NonSUL” for the servingcell, and if the UE determines that Type-1 power headroom report for theserving cell is based on a reference PUSCH transmission and Type-3 powerheadroom report for the serving cell is based on a reference SRStransmission, the UE provides the Type-1 PHR.

If a UE is configured with two UL carriers for a serving cell and if theUE reports a UE capability “simultaneousTxSUL-NonSUL” for the servingcell, and if the UE determines that a power headroom for only one of thetwo UL carriers of the serving cell is based on an actual transmission,the UE provides a Type-1 PHR when the actual transmission is a PUSCHtransmission, or provides a Type-3 PHR when the actual transmission isan SRS transmission.

In order to know at the gNB side whether the reported PHR value is atype-1 or type-3 PHR the gNB needs to know which grants are consideredfor the PH determination. Therefore, the gNB basically needs to knowwhen the PHR was generated in order to understand whether the PHR MAC CEcontains a PHR type-1 or PHR type-3 report. It should be noted that thePHR MAC CE format (multiple entry PHR MAC CE) doesn't explicitlyindicate the PHR type, according to TS 38.321 v15.3.0.

This disclosure contains embodiments providing solutions for reportingpower headroom. In a first solution, the UE signals timing informationto the RAN node such as gNB, eNB or the like indicating whether thecorresponding uplink transmission denotes the first transmission attemptor a second or later transmission attempt. In a second solution, the UEupdates the content of a MAC CE contained in a TB for each transmissionattempt. In a third solution, the UE always reports a predefined PHRtype, e.g., type-1 PHR, when the PHR MAC CE is transmitted on anunlicensed cell. In a fourth solution, a field in the PHR MAC CEindicates the type of reported PH value. In a fifth solution, the UEprioritizes transmission of a PHR MAC CE on a licensed cell overtransmissions of a PHR MAC CE on an unlicensed cell. In a sixthsolution, the UE reports a virtual PHR for a predefined PHR type, e.g.,PHR type-1, for a serving cell configured with two UL carriers.

FIG. 1

FIG. 1 depicts an embodiment of a wireless communication system 100 foraccessing a denied network resource, according to various embodiments ofthe disclosure. In one embodiment, the wireless communication system 100includes remote units 105, base units 110, and communication links 115.Even though a specific number of remote units 105, base units 110, andcommunication links 115 are depicted in FIG. 1, one of skill in the artwill recognize that any number of remote units 105, base units 110, andcommunication links 115 may be included in the wireless communicationsystem 100.

In one implementation, the wireless communication system 100 iscompliant with the NR system specified in the 3GPP specifications and/orthe LTE system specified in 3GPP. More generally, however, the wirelesscommunication system 100 may implement some other open or proprietarycommunication network, for example, WiMAX, among other networks. Thepresent disclosure is not intended to be limited to the implementationof any particular wireless communication system architecture orprotocol.

In one embodiment, the remote units 105 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), smart appliances (e.g.,appliances connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), or thelike. In some embodiments, the remote units 105 include wearabledevices, such as smart watches, fitness bands, optical head-mounteddisplays, or the like. Moreover, the remote units 105 may be referred toas subscriber units, mobiles, mobile stations, users, terminals, mobileterminals, fixed terminals, subscriber stations, UE, user terminals, adevice, or by other terminology used in the art. The remote units 105may communicate directly with one or more of the base units 110 viauplink (“UL”) and downlink (“DL”) communication signals. Furthermore,the UL and DL communication signals may be carried over thecommunication links 115.

In some embodiments, a remote unit 105 may decide to establish a dataconnection (e.g., a PDU session) with an application server (“AS”) 151in the data network 150 via the mobile core network 130. Here, the datapath of a PDU session may be established over one of the multiplenetwork slices supported by the mobile core network 130. The specificnetwork slice used by the PDU session may be determined by the S-NSSAIattribute of the PDU session. Here, the remote unit 105 may beprovisioned with Network Slice Selection Policy (“NSSP”) rules which ituses to determine how to route a requested PDU session.

The base units 110 may be distributed over a geographic region. Incertain embodiments, a base unit 110 may also be referred to as a RANnode, an access terminal, a base, a base station, a Node-B, an eNB, agNB, a Home Node-B, a relay node, a femtocell, an access point, adevice, or by any other terminology used in the art. The base units 110are generally part of an access network 120, such as a radio accessnetwork (“RAN”), that may include one or more controllers communicablycoupled to one or more corresponding base units 110. These and otherelements of the access network 120 are not illustrated but are wellknown generally by those having ordinary skill in the art. The baseunits 110 connect to the mobile core network 130 via the access network120. The access network 120 and mobile core network 130 may becollectively referred to herein as a “mobile network” or “mobilecommunication network.”

The base units 110 may serve a number of remote units 105 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The base units 110 may communicate directly with oneor more of the remote units 105 via communication signals. Generally,the base units 110 transmit downlink (“DL”) communication signals toserve the remote units 105 in the time, frequency, and/or spatialdomain. Furthermore, the DL communication signals may be carried overthe communication links 115. The communication links 115 may be anysuitable carrier in licensed or unlicensed radio spectrum. Thecommunication links 115 facilitate communication between one or more ofthe remote units 105 and/or one or more of the base units 110.

In one embodiment, the mobile core network 130 is a 5G core (“5GC”),which may be coupled to a data network 150, like the Internet andprivate data networks, among other data networks. In some embodiments,the remote units 105 communicate with an application server (“AS”) 151(external to the mobile core network 130) via a network connection withthe mobile core network 130. Each mobile core network 130 belongs to asingle public land mobile network (“PLMN”). The present disclosure isnot intended to be limited to the implementation of any particularwireless communication system architecture or protocol. For example,other embodiments of the mobile core network 130 include an enhancedpacket core (“EPC”) or a Multi-Service Core as describe by the BroadbandForum (“BBF”).

The mobile core network 130 includes several network functions (“NFs”).As depicted, the mobile core network 130 includes at least one userplane function (“UPF”) 131. The mobile core network 130 also includesmultiple control plane functions including, but not limited to, anAccess and Mobility Management Function (“AMF”) 133 that serves theaccess network 120, a Session Management Function (“SMF”) 135, a NetworkExposure Function (“NEF”) 137, a Policy Control Function (“PCF”) 138, aUnified Data Management and Unified Data Repository function (“UDM/UDR”)139. Control plane network functions provide services such as UEregistration, UE connection management, UE mobility management, sessionmanagement, and the like. In contrast, a UPF provides data transportservices to the remote units 105. In certain embodiments, the mobilecore network 130 may also include, an Authentication Server Function(“AUSF”), a Network Repository Function (“NRF”) (used by the various NFsto discover and communicate with each other over application programminginterfaces (“APIs”)), or other NFs defined for the 5GC.

The NEF 137 supports exposure of capabilities and events, secureprovision of information from external application to 3GPP network,translation of internal/external information. The UDM/UDR 139 comprisesa Unified Data Management (“UDM”) and its internal component User DataRepository (“UDR”). The UDR holds subscription data including policydata. Specifically, the policy data stored by the UDM/UDR 139 includesthe NSSP.

Although specific numbers and types of network functions are depicted inFIG. 1, one of skill in the art will recognize that any number and typeof network functions may be included in the mobile core network 130.Moreover, where the mobile core network 130 is an EPC, the depictednetwork functions may be replaced with appropriate EPC entities, such asan MME, SGW, PGW, HSS, and the like. In certain embodiments, the mobilecore network 130 may include an authentication, authorization, andaccounting (“AAA”) server.

In various embodiments, the mobile core network 130 supports differenttypes of mobile data connections and different types of network slices,wherein each mobile data connection utilizes a specific network slice.Here, a “network slice” refers to a portion of the mobile core network130 optimized for a certain traffic type or communication service. Incertain embodiments, the various network slices may include separateinstances of network functions, such as the SMF 135 and UPF 131. In someembodiments, the different network slices may share some common networkfunctions, such as the AMF 133. The different network slices are notshown in FIG. 1 for ease of illustration, but their support is assumed.

The network slices are logical networks within the mobile core network130. In certain embodiments, the network slices are partitions ofresources and/or services of the mobile core network 130. Differentnetwork slices may be used to meet different service needs (e.g.,latency, reliability, and capacity). Examples of different types ofnetwork slices include enhanced mobile broadband (“eMBB”), massivemachine-type communication (“mMTC”), and ultra-reliability and lowlatency communications (“URLLC”). A mobile core network 130 may includemultiple network slice instances of the same network slice type.Different network slice instance of the same type may be distinguishedby a slice “tenant” (also known as “slice differentiator”) associatedwith the instance.

Due to LBT failures the base unit 110 might not be aware of the timewhen the UE generated the TB transmitted on a configured grant resourceand hence is not aware of when the PHR was calculated. There arebasically two problems caused by this timing uncertainty. The firstissue is that the base unit 110 doesn't know for which UL resourceallocation, e.g. PRBs allocated in the slot for which PHR wascalculated, the PH was calculated/reported and hence may draw some wrongconclusions for the future scheduling. Secondly the base unit 110 maynot be aware of the reported PHR type—for cases when a serving cell isconfigured with two UL carriers—and may hence interpret the reported PHvalues incorrectly which in turn may lead to future scheduling decisionsnegatively impacting the performance.

To resolve the above noted problems with PHR reporting for an AULtransmission 125, a remote unit 105 may perform one or more of:communicate timing information as part of AUL-UCI, update PH values forsecond/subsequent transmission attempts, always report using apredefined PHR type when transmitting a PHR MAC CE on an AUL PUSCH,and/or apply a policy rule for PHR type.

According to a first solution, the remote unit 105 signals timinginformation related to the calculation of the power headroom informationto the base unit 110 (a RAN node, such as gNB, eNB or the like)indicating whether the corresponding uplink transmission correspondsto 1) a first transmission attempt or 2) a second or later transmissionattempt. Because the remote unit 105 must first undergo a CCA (ClearChannel Assessment) procedure before a transmission can be made on theunlicensed spectrum, the remote unit 105 may be unable to transmit agenerated TB immediately at the first transmission occasion/attempt,e.g., due to the CCA procedure not being successful for the firsttransmission attempt, but may only be able to transmit the generated TBat a later point of time when LBT (Listen Before Talk) is successful.

The timing information may be used by the base unit 110 (RAN node) forfuture scheduling/link adaption. In particular when receiving a PHR MACCE, it is important to be aware at the base unit 110 when the PHRinformation was calculated in the remote unit 105, in order to interpretthe reported PH values correctly.

According to one implementation of the first solution, the timinginformation may be signaled by a one-bit field/flag. For example, whenset to ‘1’ the flag indicates that uplink transmission takes place atthe first transmission occasion/attempt, e.g., CCA was successful.Similarly, the flag set to ‘0’ indicates that the uplink transmission isdone at the second or later transmission attempt, e.g., generated TBcouldn't be transmitted immediately because CCA wasn't successful. Inother embodiments, the flag values may be switched such that a value of‘0’ indicated a first transmission attempt and a value of ‘1’ indicatesa second or later transmission attempt.

According to another implementation of the first solution, the timinginformation may indicate the offset (e.g., in number of frames, slots,subframes, or symbols) to the first transmission attempt using multiplebits. In case CCA is successful for the first transmission attempt,e.g., generated TB is immediately transmitted on corresponding nextavailable PUSCH occasion, the timing information would indicate a “zero”slot/symbol offset. Accordingly, when the transmission of the TB takesplace 5 slots after the first transmission attempt, e.g., LBT failedbefore, the timing information will indicate a 5 slot offset. As analternative, the timing information may indicate the number oftransmission attempts respectively the number of LBT failures for the TBuntil CCA was successful, e.g., using multiple bits.

According to certain implementations of the first solution, the timinginformation is transmitted as part of uplink control information (UCI),which is transmitted independently from the PUSCH transmission(transport block). The UCI conveying the timing information is encodedseparately from the PUSCH data. Hence, the base unit 110 receiver willdecode the UCI separately form the PUSCH. In one implementation of thefirst embodiment the timing information is carried within the AUL-UCI.

FIG. 2

FIG. 2 depicts one embodiment of an AUL-UCI 200, according toembodiments of the disclosure. The AUL-UCI 200 contains a plurality offields, including the AUL-RNTI 205, the HARQ process number 210, theredundancy version (“RV”) 215, a New Data Indicator (“NDI”) 220, thePUSCH starting symbol 225, the PUSCH ending symbol 230, and channeloccupancy time (“COT”) sharing indication 235. Importantly, the AUL-UCI200 contains a ‘PH timing information’ field 240,_([JL1][BWP2])indicating timing related to the calculation of the powerheadroom information. As depicted, the PH timing information 240 may berepresented by three bits in the AUL-UCI. In one embodiment, the PHtiming information 240 indicates the number of transmission attempts. Inanother embodiment, the PH timing information 240 indicates the offsetto the first transmission attempt. The information carried within thisfield is used in the scheduler/gNB for future scheduling/link adaption.It basically provides the base unit 110 with the information when the TBwas generated.

According to a second solution, the remote unit 105 updates the contentof a MAC CE contained in a TB for each transmission attempt. Forexample, in case a generated TB was unable to be transmitted at atransmission (PUSCH) occasion due to LBT failure, the remote unit 105will update the content of the MAC CEs carried within the TB for thenext transmission attempt. Put another way, the MAC CEs in a TB are toalways indicate the most up-to date values.

In particular, for a PHR MAC CE contained in a TB, the remote unit 105may update the reported PH values for each transmission attempt suchthat the base unit 110—when receiving a PHR MAC CE—is aware of when thereported PH values were calculated, e.g., the base unit 110 knows whatcontrol information (such as uplink grants and configured grants) wereconsidered for the calculation of the reported PHR. The second solutionalso ensures that the base unit 110 is aware of what type of PHR isreported within the PHR MAC CE, e.g., whether type-1 or type-3 PHR isreported for a cell configured with two UL carriers (SUL and NUL).

Apart from the PHR MAC CE, also it may be beneficial for the schedulerto update the BSR MAC CE indicating the buffer status of the remote unit105 for each transmission attempt. According to one implementation ofthe second embodiment only the values reported within a MAC CE, e.g.,PHR MAC CE, are updated for each transmission attempt, but the PDUformat of the MAC CE is not changed. Doing so ensures that the remoteunit 105 doesn't need to run the logical channel prioritization (LCP)procedure again.

According to a third solution, the remote unit 105 always reports apredefined PHR type, e.g., type-1 PHR, for a serving cell which isconfigured with two (uplink) carriers (e.g., SUL and NUL) and/or forcases when the PHR MAC CE is transmitted on an unlicensed serving cell.As mentioned above, according to the current defined UE behavior instandards, the remote unit 105 reports either a type-1 or type-3 PHRreport for a serving cell configured with two carriers depending onwhether an actual PUSCH or SRS transmission takes place on the carriersin the reporting slot. Therefore, the base unit 110 needs to know whenthe remote unit 105 determined the PHR types for the serving cells inorder to know what information is included in the PHR MAC CE, e.g., PHRtype-1 or PHR type-3.

According to various implementations of the third solution, anew/special rule for PHR value determination (PHR type-1 versus PHRtype-3) may be used for cases when PHR MAC CE is transmitted on anunlicensed cell compared to cases where the PHR MAC CE is transmitted ona licensed cell. This new rule ensures that the gNB is always aware ofwhich PHR type, e.g., type-1 or type-3 PHR, is signaled within a PHR MACCE.

According to one implementation of the third solution the remote unit105 always reports using a predefined PHR type, e.g., type-1 PHR, for aserving cell which is configured with two carriers, e.g., SUL and NUL,and for cases when the PHR MAC CE is transmitted on an AUL PUSCH. Forscheduled PUSCH transmission on an unlicensed cell, legacy UE reportingbehavior with respect to PHR reporting is applied.

One implementation of the third solution maybe described using thefollowing rule: If a UE (remote unit 105) is configured with two ULcarriers for a serving cell and if the UE reports a UE capabilitysimultaneousTxSUL-NonSUL for the serving cell, and if a PHR istransmitted on an AUL-PUSCH, then the UE (remote unit 105) provides aType-1 PHR for the serving cell.

According to a fourth solution, a field in the PHR MAC CE indicates thetype of the reported PH value, e.g., whether PHR type-1 or PHR type-3.According to one implementation of the fourth solution, at least one ofthe ‘reserved’ fields in the octet where P_(CMAX) is signaled for aserving cell is used for indicating the PHR type. In one implementationone of the reserved fields ‘R,’ when set to ‘1’, may indicate that thePH value is a type-1 PH value. Accordingly, when set to ‘0’ thecorresponding reported PH value is a type-3 PH value. In anotherimplementation both ‘R’ fields may be used to indicate the PHR type(e.g., to distinguish between up to four different PHR types).

FIG. 3

FIG. 3 depicts one embodiment of a MAC PDU format 300 for the PHR MACCE, according to embodiments of the invention. The MAC PDU format 300may be used to implement the fourth solution described herein. It shouldbe noted that this shown option should be only understood as an exampleof an implementation. As depicted, the exemplary MAC PDU format for thePHR MAC CE contains a new field, denoted as ‘T,’ which indicates the PHRtype. One (or both) of the ‘R’ fields in the octet including _(CMAX) isreused as the new ‘T’ field.

According to a fifth solution, the remote unit 105 prioritizestransmission of a PHR MAC CE on a licensed cell over transmissions of aPHR MAC CE on an unlicensed cell. Here, for cases when there are PUSCHresources available for an initial transmission on a licensed cell aswell as for an unlicensed cell, the remote unit 105 transmits a PHR MACCE, e.g., PHR has been triggered before, on the PUSCH resources of thelicensed cell. According to one implementation of the fifth solution,where the remote unit 105 is configured with at least one licensed celland at least one unlicensed cell, then the remote unit 105 alwaystransmits a PHR MAC CE on a licensed cell, e.g., PHR MAC CE are notallowed to be transmitted on an unlicensed cell. According to anotherimplementation of the fifth solution, the remote unit 105 is not totransmit a PHR MAC CE on an AUL-PUSCH. Here, when performing the LCPprocedure for an AUL transmission, the remote unit 105 is not tomultiplex a PHR MAC CE in the transport block.

According to a sixth solution, a remote unit 105 (e.g., UE) configuredwith carrier aggregation reports a virtual PHR for a predefined PHRtype, e.g., PHR type-1, for a serving cell configured with two ULcarriers. Further, the remote unit 105 reports a virtual PHR for otheractivated serving cells (with configured uplink) for cases when 1) thePHR MAC CE is transmitted on a configured grant, e.g., PUSCH resourcesallocated by a configured grant, on an unlicensed cell or 2) when thePHR MAC CE is transmitted on a configured grant PUSCH resource and theMAC entity is configured with lch-basedPrioritization. According to thisimplementation of the sixth solution, remote unit 105 reports for allactivated serving cells (with configured uplink) a virtual PHR—for aserving cell configured with two UL carrier a virtual PHR for apredefined PHR type, e.g., PHR type-1.

According to one alternative implementation of the sixth solution, theremote unit 105 reports actual PHR for the serving cell on which the PHRMAC CE is transmitted and reports a virtual PHR for other activatedserving cells (with configured uplink). Further, if a serving cell isconfigured with two UL carriers, then the remote unit 105 reports avirtual PHR for a predefined PHR type for cases when the PHR MAC CE istransmitted on a configured grant on an unlicensed cell or for caseswhen the PHR MAC CE is transmitted on a configured grant PUSCH resourceand the MAC entity is configured with lch-basedPrioritization.

Reporting a predefined/fixed PHR type of a serving cell configured withtwo UL carriers solves the issue of the base unit 110 (e.g., gNB) notbeing aware of the reported PHR type. Reporting a virtual PHR solves theissue of the base unit 110 (e.g., gNB) not knowing for which UL resourceallocation(s) the PH was calculated. It should be noted that the sameproblems may also occur for cases when a configured grant PUSCHtransmission is pre-empted or deprioritized due to some higher priorityUL transmission requiring an overlapping PUSCH resource. For example,the configured grant may be preempted by a later received dynamic ULgrant scheduling an overlapping PUSCH resource. Therefore, according tothe sixth solution, the remote unit 105 configured with carrieraggregation reports a virtual PHR for a predefined PHR type, e.g., PHRtype-1, for a serving cell configured with two UL carriers and reports avirtual PHR for other activated serving cells (with configured uplink)for cases when the MAC entity is configured withlch-basedPrioritization. The condition “configured withlch-basedPrioritization” refers to the case where the network (e.g.,base unit 110) configures the remote unit 105 to allow a (low) priorityUL transmission to be deprioritized/preempted by some (later) highpriority UL grant/transmissions, which is a new feature of theIndustrial IOT WI. It is assumed that the prioritization mechanismfeature is configured per UE for backward compatibility and separationfrom UEs not supporting this feature. This terminology may be changedlater during further discussions in 3GPP.

According to another embodiment, a remote unit 105 not configured withcarrier aggregation reports a virtual PHR for the serving cell for caseswhen the PHR MAC CE is transmitted on a configured grant, e.g., PUSCHresources allocated by a configured grant, and the serving cell is anunlicensed cell as well as for cases when the PHR MAC CE is transmittedon a configured grant PUSCH resource and the MAC entity is configuredwith lch-basedPrioritization. According to one implementation of thisembodiment UE reports a P_(CMAX,f,c) value within the single-entry PHRMAC CE even for the case that virtual PHR is reported.

FIG. 4—UE Apparatus 400

FIG. 4 depicts a user equipment apparatus 400 that may be used for PHRreporting, according to embodiments of the disclosure. In variousembodiments, the user equipment apparatus 400 is used to implement oneor more of the solutions described above. The user equipment apparatus400 may be one embodiment of the remote unit 105, described above.Furthermore, the user equipment apparatus 400 may include a processor405, a memory 410, an input device 415, an output device 420, and atransceiver 425. In some embodiments, the input device 415 and theoutput device 420 are combined into a single device, such as atouchscreen. In certain embodiments, the user equipment apparatus 400may not include any input device 415 and/or output device 420. Invarious embodiments, the user equipment apparatus 400 may include one ormore of: the processor 405, the memory 410, and the transceiver 425, andmay not include the input device 415 and/or the output device 420.

The processor 405, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 405 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 405 executes instructions stored in thememory 410 to perform the methods and routines described herein. Theprocessor 405 is communicatively coupled to the memory 410, the inputdevice 415, the output device 420, and the transceiver 425.

In various embodiments, the processor 405 identifies a transmissionoccasion for AUL transmission on an unlicensed serving cell andgenerates a PHR MAC CE. The transceiver 425 then transmits the PHR MACCE with an AUL transmission to a RAN node in the mobile communicationnetwork. Here, transmitting the PHR MAC CE includes indicating timinginformation corresponding to the PHR. In some embodiments, the timinginformation provides information to the RAN node on the firsttransmission attempt of the PHR MAC CE. In some embodiments, the timinginformation includes a one-bit flag, wherein a first value of theone-bit flag indicates that the PHR MAC CE transmission corresponds to afirst transmission attempt and a second value of the one-bit flagindicates that the PHR MAC CE transmission corresponds to a subsequenttransmission attempt.

In some embodiments, the timing information includes an indication of atiming offset between the PHR MAC CE transmission and a firsttransmission attempt. In one embodiment, the timing offset indicates anumber of slots elapsed since the first transmission attempt. In anotherembodiment, the timing offset indicates a number of symbols elapsedsince the first transmission attempt. In some embodiments, the timinginformation includes an indication of a number of transmission attemptsprior to the PHR transmission. In some embodiments, the timinginformation is transmitted as part of uplink control information and isencoded separately from the PHR.

In various embodiments, the processor 405 identifies a firsttransmission occasion for AUL transmission on an unlicensed servingcell. The processor 405 generates a PHR MAC CE including power headroominformation for each activated serving cell configured with uplink.Here, the power headroom information for an activated serving cell iscalculated for a predetermined PHR type in response to the serving cellbeing configured with two UL carriers. The transceiver 425 that thentransmits the PHR MAC CE in an AUL transmission to a RAN node in themobile communication network. In some embodiments, the processor 405prioritizes transmitting the PHR MAC CE on a licensed cell overtransmitting the PHR on the unlicensed serving cell.

In various embodiments, the processor 405 identifies a firsttransmission occasion on a configured uplink grant resource. Theprocessor 405 generates a PHR MAC CE including power headroominformation for each activated serving cell. Here, the power headroominformation is calculated for a predetermined PHR type in response to aserving cell being configured with two UL carriers. The transceiver 425then transmits the PHR MAC CE in a configured grant transmission to aRAN node in the mobile communication network.

In some embodiments, generating the PHR MAC CE includes reporting avirtual power headroom for each activated serving cell in response tothe PHR MAC CE being transmitted on a configured uplink grant andfurther in response to a MAC entity of the user equipment apparatus 400being configured to deprioritize a lower priority uplink transmission infavor of a higher priority uplink transmission. In such embodiments,preparing the PHR MAC CE includes reporting a virtual PHR for apredefined PHR type in response to a serving cell being configured withtwo UL carriers.

In some embodiments, that user equipment apparatus 400 is configured forcarrier aggregation using multiple activated serving cells, whereinpreparing the PHR MAC CE includes reporting an actual PHR for theserving cell on which the PHR MAC CE is to be transmitted and reportingvirtual PHR for one or more other activated serving cells.

The memory 410, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 410 includes volatile computerstorage media. For example, the memory 410 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 410 includes non-volatilecomputer storage media. For example, the memory 410 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 410 includes bothvolatile and non-volatile computer storage media.

In some embodiments, the memory 410 stores data related to powerheadroom reporting. For example, the memory 410 may store PH values, AULdata, AUL configuration information, timing offsets, and the like. Incertain embodiments, the memory 410 also stores program code and relateddata, such as an operating system or other controller algorithmsoperating on the remote unit 105.

The input device 415, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 415 maybe integrated with the output device 420, for example, as a touchscreenor similar touch-sensitive display. In some embodiments, the inputdevice 415 includes a touchscreen such that text may be input using avirtual keyboard displayed on the touchscreen and/or by handwriting onthe touchscreen. In some embodiments, the input device 415 includes twoor more different devices, such as a keyboard and a touch panel.

The output device 420, in one embodiment, is designed to output visual,audible, and/or haptic signals. In some embodiments, the output device420 includes an electronically controllable display or display devicecapable of outputting visual data to a user. For example, the outputdevice 420 may include, but is not limited to, an LCD display, an LEDdisplay, an OLED display, a projector, or similar display device capableof outputting images, text, or the like to a user. As another,non-limiting, example, the output device 420 may include a wearabledisplay separate from, but communicatively coupled to, the rest of theuser equipment apparatus 400, such as a smart watch, smart glasses, aheads-up display, or the like. Further, the output device 420 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the output device 420 includes one or morespeakers for producing sound. For example, the output device 420 mayproduce an audible alert or notification (e.g., a beep or chime). Insome embodiments, the output device 420 includes one or more hapticdevices for producing vibrations, motion, or other haptic feedback. Insome embodiments, all or portions of the output device 420 may beintegrated with the input device 415. For example, the input device 415and output device 420 may form a touchscreen or similar touch-sensitivedisplay. In other embodiments, the output device 420 may be located nearthe input device 415.

As discussed above, the transceiver 425 communicates with one or morenetwork functions of a mobile communication network via one or moreaccess networks. The transceiver 425 operates under the control of theprocessor 405 to transmit messages, data, and other signals and also toreceive messages, data, and other signals. For example, the processor405 may selectively activate the transceiver 425 (or portions thereof)at particular times in order to send and receive messages.

The transceiver 425 may include one or more transmitters 430 and one ormore receivers 435. Although only one transmitter 430 and one receiver435 are illustrated, the user equipment apparatus 400 may have anysuitable number of transmitters 430 and receivers 435. Further, thetransmitter(s) 430 and the receiver(s) 435 may be any suitable type oftransmitters and receivers. Additionally, the transceiver 425 maysupport at least one network interface 440. Here, the at least onenetwork interface 440 facilitates communication with a RAN node, such asan eNB or gNB, for example using the “Uu” interface. Additionally, theat least one network interface 440 may include an interface used forcommunications with one or more network functions in the mobile corenetwork, such as a UPF, an AMF, and/or a SMF.

In one embodiment, the transceiver 425 includes a firsttransmitter/receiver pair used to communicate with a mobilecommunication network over licensed radio spectrum and a secondtransmitter/receiver pair used to communicate with a mobilecommunication network over unlicensed radio spectrum. In certainembodiments, the first transmitter/receiver pair used to communicatewith a mobile communication network over licensed radio spectrum and thesecond transmitter/receiver pair used to communicate with a mobilecommunication network over unlicensed radio spectrum may be combinedinto a single transceiver unit, for example a single chip performingfunctions for use with both licensed and unlicensed radio spectrum. Insome embodiments, the first transmitter/receiver pair and the secondtransmitter/receiver pair may share one or more hardware components. Forexample, certain transceivers 425, transmitters 430, and receivers 435may be implemented as physically separate components that access ashared hardware resource and/or software resource, such as for example,the network interface 440.

In various embodiments, one or more transmitters 430 and/or one or morereceivers 435 may be implemented and/or integrated into a singlehardware component, such as a multi-transceiver chip, asystem-on-a-chip, an application-specific integrated circuit (“ASIC”),or other type of hardware component. In certain embodiments, one or moretransmitters 430 and/or one or more receivers 435 may be implementedand/or integrated into a multi-chip module. In some embodiments, othercomponents such as the network interface 440 or other hardwarecomponents/circuits may be integrated with any number of transmitters430 and/or receivers 435 into a single chip. In such embodiment, thetransmitters 430 and receivers 435 may be logically configured as atransceiver 425 that uses one more common control signals or as modulartransmitters 430 and receivers 435 implemented in the same hardware chipor in a multi-chip module.

FIG. 5—GNB that Receives PHR

FIG. 5 depicts a base station apparatus 500 that may be used forreporting power headroom, according to embodiments of the disclosure.The base station apparatus 500 may be one embodiment of the remote unit105 or UE, described above. Furthermore, the base station apparatus 500may include a processor 505, a memory 510, an input device 515, anoutput device 520, and a transceiver 525. In some embodiments, the inputdevice 515 and the output device 520 are combined into a single device,such as a touchscreen. In certain embodiments, the base stationapparatus 500 may not include any input device 515 and/or output device520. In various embodiments, the base station apparatus 500 may includeone or more of: the processor 505, the memory 510, and the transceiver525, and may not include the input device 515 and/or the output device520.

The processor 505, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 505 may be amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or similar programmable controller. In some embodiments,the processor 505 executes instructions stored in the memory 510 toperform the methods and routines described herein. The processor 505 iscommunicatively coupled to the memory 510, the input device 515, theoutput device 520, and the transceiver 525.

In various embodiments, the base station apparatus 500 receives (e.g.,via the transceiver 525) a PHR from a served UE. Additionally, the basestation apparatus 500 may receive timing information relating to thePHR, as described herein. Using the timing information, the processor505 interprets the reported power headroom values.

In various embodiments, the processor 505 identifies a number of uplinkcarriers for a serving cell of the UE. The processor 505 may use theconfiguration of uplink carriers to interpret the reported powerheadroom values, for example inferring PHR type (e.g., type-1 or type-3)from the uplink carrier configuration and/or inferring actual or virtualPHR from the uplink carrier configuration.

The memory 510, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 510 includes volatile computerstorage media. For example, the memory 510 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 510 includes non-volatilecomputer storage media. For example, the memory 510 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 510 includes bothvolatile and non-volatile computer storage media.

In some embodiments, the memory 510 stores data related to reportingpower headroom. For example, the memory 510 may store PH timinginformation, UL carrier configurations, PHR values, and the like. Incertain embodiments, the memory 510 also stores program code and relateddata, such as an operating system or other controller algorithmsoperating on the remote unit 105.

The input device 515, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 515 maybe integrated with the output device 520, for example, as a touchscreenor similar touch-sensitive display. In some embodiments, the inputdevice 515 includes a touchscreen such that text may be input using avirtual keyboard displayed on the touchscreen and/or by handwriting onthe touchscreen. In some embodiments, the input device 515 includes twoor more different devices, such as a keyboard and a touch panel.

The output device 520, in one embodiment, is designed to output visual,audible, and/or haptic signals. In some embodiments, the output device520 includes an electronically controllable display or display devicecapable of outputting visual data to a user. For example, the outputdevice 520 may include, but is not limited to, an LCD display, an LEDdisplay, an OLED display, a projector, or similar display device capableof outputting images, text, or the like to a user. As another,non-limiting, example, the output device 520 may include a wearabledisplay separate from, but communicatively coupled to, the rest of thebase station apparatus 500, such as a smart watch, smart glasses, aheads-up display, or the like. Further, the output device 520 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the output device 520 includes one or morespeakers for producing sound. For example, the output device 520 mayproduce an audible alert or notification (e.g., a beep or chime). Insome embodiments, the output device 520 includes one or more hapticdevices for producing vibrations, motion, or other haptic feedback. Insome embodiments, all or portions of the output device 520 may beintegrated with the input device 515. For example, the input device 515and output device 520 may form a touchscreen or similar touch-sensitivedisplay. In other embodiments, the output device 520 may be located nearthe input device 515.

The transceiver 525 includes at least transmitter 530 and at least onereceiver 535. One or more transmitters 530 may be used to communicatewith the UE, as described herein. Similarly, one or more receivers 535may be used to communicate with other network functions in the PLMN, asdescribed herein. Although only one transmitter 530 and one receiver 535are illustrated, the base station apparatus 500 may have any suitablenumber of transmitters 530 and receivers 535. Further, thetransmitter(s) 525 and the receiver(s) 530 may be any suitable type oftransmitters and receivers.

AUL UE Method 600

FIG. 6 depicts one embodiment of a method 600 for reporting powerheadroom, according to embodiments of the disclosure. In variousembodiments, the method 600 is performed by the remote unit 105 and/orthe user equipment apparatus 400, described above. In some embodiments,the method 600 is performed by a processor, such as a microcontroller, amicroprocessor, a central processing unit (CPU), a graphics processingunit (GPU), an auxiliary processing unit, a FPGA, or the like.

The method 600 begins and identifies 605 a transmission occasion for AULtransmission on an unlicensed serving cell. The method 600 includesgenerating 610 a PHR MAC CE. The method 600 includes transmitting 615the PHR MAC CE with an AUL transmission to a RAN node in the mobilecommunication network. Here, transmitting the PHR MAC CE includesindicating timing information corresponding to the PHR. The method 600ends.

AUL+CA UE Method 700

FIG. 7 depicts one embodiment of a method 700 for reporting powerheadroom, according to embodiments of the disclosure. In variousembodiments, the method 700 is performed by a UE, such as the remoteunit 105 and/or the user equipment apparatus 400, described above. Insome embodiments, the method 700 is performed by a processor, such as amicrocontroller, a microprocessor, a central processing unit (CPU), agraphics processing unit (GPU), an auxiliary processing unit, a FPGA, orthe like.

The method 700 begins and identifies 705 a first transmission occasionfor AUL transmission on an unlicensed serving cell. The method 700includes generating 710 a PHR MAC CE including power headroominformation for each activated serving cell configured with uplink.Here, the power headroom information for an activated serving cell iscalculated for a predetermined PHR type in response to the serving cellbeing configured with two UL carriers. The method 800 includestransmitting 715 the PHR MAC CE in an AUL transmission to a RAN node inthe mobile communication network. The method 700 ends.

CA UE Method 800

FIG. 8 depicts one embodiment of a method 800 for reporting powerheadroom, according to embodiments of the disclosure. In variousembodiments, the method 800 is performed by a UE, such as the remoteunit 105 and/or the user equipment apparatus 400, described above. Insome embodiments, the method 800 is performed by a processor, such as amicrocontroller, a microprocessor, a central processing unit (CPU), agraphics processing unit (GPU), an auxiliary processing unit, a FPGA, orthe like.

The method 800 begins and identifies 805 a first transmission occasionon a configured uplink grant resource. The method 800 includesgenerating 810 a PHR MAC CE including power headroom information foreach activated serving cell.

The method 800 includes transmitting 815 the PHR MAC CE to a RAN node inthe mobile communication network. Here, the power headroom informationis calculated for a predetermined PHR type in response to a serving cellbeing configured with two UL carriers. The method 800 ends.

Claim Statements AUL UE Apparatus

Disclosed herein is a first apparatus for reporting power headroom,according to embodiments of the disclosure. The first apparatus may beimplemented by a UE, such as the remote unit 105 and/or the userequipment apparatus 400. The first apparatus includes a processor thatidentifies a transmission occasion for AUL transmission on an unlicensedserving cell and generates a PHR MAC CE. The first apparatus includes atransceiver that transmits the PHR MAC CE with an AUL transmission to aRAN node in the mobile communication network, wherein transmitting thePHR MAC CE includes indicating timing information corresponding to thePHR.

In some embodiments, the timing information provides information to theRAN node on the first transmission attempt of the PHR MAC CE. In someembodiments, the timing information includes a one-bit flag, wherein afirst value of the one-bit flag indicates that the PHR MAC CEtransmission corresponds to a first transmission attempt and a secondvalue of the one-bit flag indicates that the PHR MAC CE transmissioncorresponds to a subsequent transmission attempt.

In some embodiments, the timing information includes an indication of atiming offset between the PHR MAC CE transmission and a firsttransmission attempt. In one embodiment, the timing offset indicates anumber of slots elapsed since the first transmission attempt. In anotherembodiment, the timing offset indicates a number of symbols elapsedsince the first transmission attempt.

In some embodiments, the timing information includes an indication of anumber of transmission attempts prior to the PHR transmission. In someembodiments, the timing information is transmitted as part of uplinkcontrol information and is encoded separately from the PHR.

AUL UE Method

Disclosed herein is a first method for reporting power headroom,according to embodiments of the disclosure. The first method may beperformed by a UE, such as the remote unit 105 and/or the user equipmentapparatus 400. The first method includes identifying a transmissionoccasion for AUL transmission on an unlicensed serving cell. The firstmethod includes generating a PHR MAC CE and transmitting the PHR MAC CEwith an AUL transmission to a RAN node in the mobile communicationnetwork, wherein transmitting the PHR MAC CE includes indicating timinginformation corresponding to the PHR.

In some embodiments of the first method, the timing information providesinformation to the RAN node on the first transmission attempt of the PHRMAC CE. In some embodiments of the first method, the timing informationincludes a one-bit flag, wherein a first value of the one-bit flagindicates that the PHR MAC CE transmission corresponds to a firsttransmission attempt and a second value of the one-bit flag indicatesthat the PHR MAC CE transmission corresponds to a subsequenttransmission attempt.

In some embodiments of the first method, the timing information includesan indication of a timing offset between the PHR MAC CE transmission anda first transmission attempt. In one embodiment, the timing offsetindicates a number of slots elapsed since the first transmissionattempt. In another embodiment, the timing offset indicates a number ofsymbols elapsed since the first transmission attempt.

In some embodiments of the first method, the timing information includesan indication of a number of transmission attempts prior to the PHRtransmission. In some embodiments of the first method, the timinginformation is transmitted as part of uplink control information and isencoded separately from the PHR.

AUL+CA UE Apparatus

Disclosed herein is a second apparatus for reporting power headroom,according to embodiments of the disclosure. The second apparatus may beimplemented by a UE configured for carrier aggregation using multipleserving cells for power headroom reporting in a mobile communicationnetwork, such as the remote unit 105 and/or the user equipment apparatus400. The second apparatus includes a processor that identifies a firsttransmission occasion for AUL transmission on an unlicensed servingcell. The processor generates a PHR MAC CE including power headroominformation for each activated serving cell configured with uplink,wherein the power headroom information for an activated serving cell iscalculated for a predetermined PHR type in response to the serving cellbeing configured with two UL carriers. The second apparatus includes atransceiver that transmits the PHR MAC CE in an AUL transmission to aRAN node in the mobile communication network.

In some embodiments, the processor prioritizes transmitting the PHR MACCE on a licensed cell over transmitting the PHR on the unlicensedserving cell.

AUL+CA UE Method

Disclosed herein is a second method for reporting power headroom,according to embodiments of the disclosure. The second method may beperformed by a UE configured for carrier aggregation using multipleserving cells for power headroom reporting in a mobile communicationnetwork, such as the remote unit 105 and/or the user equipment apparatus400. The second method includes identifying a first transmissionoccasion for AUL transmission on an unlicensed serving cell andgenerating a PHR MAC CE including power headroom information for eachactivated serving cell configured with uplink, wherein the powerheadroom information for an activated serving cell is calculated for apredetermined PHR type in response to the serving cell being configuredwith two UL carriers. The second method includes transmitting the PHRMAC CE in an AUL transmission to a RAN node in the mobile communicationnetwork.

In some embodiments, the second method further includes prioritizingtransmission of the PHR MAC CE on a licensed cell over transmitting thePHR on the unlicensed serving cell.

CA UE Apparatus

Disclosed herein is a third apparatus for reporting power headroom,according to embodiments of the disclosure. The third apparatus may beimplemented by a UE configured with carrier aggregation for powerheadroom reporting in a mobile communication network, such as the remoteunit 105 and/or the user equipment apparatus 400. The third apparatusincludes a processor that identifies a first transmission occasion on aconfigured uplink grant resource and generates a PHR MAC CE includingpower headroom information for each activated serving cell, wherein thepower headroom information is calculated for a predetermined PHR type inresponse to a serving cell being configured with two UL carriers. Thethird apparatus includes a transceiver that transmits the PHR MAC CE ina configured grant transmission to a RAN node in the mobilecommunication network.

In some embodiments, generating the PHR MAC CE includes reporting avirtual power headroom for each activated serving cell in response tothe PHR MAC CE being transmitted on a configured uplink grant andfurther in response to a MAC entity of the apparatus being configured todeprioritize a lower priority uplink transmission in favor of a higherpriority uplink transmission. In such embodiments, preparing the PHR MACCE includes reporting a virtual PHR for a predefined PHR type inresponse to a serving cell being configured with two UL carriers.

In some embodiments, that apparatus is configured for carrieraggregation using multiple activated serving cells, wherein preparingthe PHR MAC CE includes reporting an actual PHR for the serving cell onwhich the PHR MAC CE is to be transmitted and reporting virtual PHR forone or more other activated serving cells.

CA UE Method

Disclosed herein is a third method for reporting power headroom,according to embodiments of the disclosure. The third method may beperformed by a UE configured with carrier aggregation for power headroomreporting in a mobile communication network, such as the remote unit 105and/or the user equipment apparatus 400. The third method includesidentifying a first transmission occasion on a configured uplink grantresource. The third method includes generating a PHR MAC CE includingpower headroom information for each activated serving cell andtransmitting the PHR MAC CE to a RAN node in the mobile communicationnetwork. Here, the power headroom information is calculated for apredetermined PHR type in response to a serving cell being configuredwith two UL carriers.

In some embodiments of the third method, generating the PHR MAC CEincludes reporting a virtual power headroom for each activated servingcell in response to the PHR MAC CE being transmitted on a configureduplink grant and further in response to a MAC entity of the UE beingconfigured to deprioritize a lower priority uplink transmission in favorof a higher priority uplink transmission. In such embodiments, preparingthe PHR MAC CE includes reporting a virtual PHR for a predefined PHRtype in response to a serving cell being configured with two ULcarriers.

In some embodiments of the third method, the UE is configured forcarrier aggregation using multiple activated serving cells, whereinpreparing the PHR MAC CE includes reporting an actual PHR for theserving cell on which the PHR MAC CE is to be transmitted and reportingvirtual PHR for one or more other activated serving cells.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. A method of a UE for power headroom reporting in a mobilecommunication network, the method comprising: identifying a transmissionoccasion for autonomous uplink (“AUL”) transmission on an unlicensedserving cell; generating a power headroom report (“PHR”) Medium AccessControl (“MAC”) Control Element (“CE”); and transmitting the PHR MAC CEwith an AUL transmission to a radio access network (“RAN”) node in themobile communication network, wherein transmitting the PHR MAC CEcomprises indicating timing information corresponding to the PHR.
 2. Themethod of claim 1, wherein the timing information provides informationto the RAN node on a first transmission attempt of the PHR MAC CE. 3.The method of claim 1, wherein the timing information comprises aone-bit flag, wherein a first value of the one-bit flag indicates thatthe PHR MAC CE transmission corresponds to a first transmission attemptand a second value of the one-bit flag indicates that the PHR MAC CEtransmission corresponds to a subsequent transmission attempt.
 4. Themethod of claim 1, wherein the timing information comprises anindication of a timing offset between the PHR MAC CE transmission and afirst transmission attempt.
 5. The method of claim 1, wherein the timinginformation is transmitted as part of uplink control information and isencoded separately from the PHR.
 6. A UE apparatus for power headroomreporting in a mobile communication network, the apparatus comprising: aprocessor that: identifies a transmission occasion for autonomous uplink(“AUL”) transmission on an unlicensed serving cell, and generates apower headroom report (“PHR”) Medium Access Control (“MAC”) ControlElement (“CE”); and a transceiver that transmits the PHR MAC CE with anAUL transmission to a radio access network (“RAN”) node in the mobilecommunication network, wherein transmitting the PHR MAC CE comprisesindicating timing information corresponding to the PHR.
 7. The apparatusof claim 6, wherein the timing information provides information to theRAN node on a first transmission attempt of the PHR MAC CE.
 8. Theapparatus of claim 6, wherein the timing information comprises a one-bitflag, wherein a first value of the one-bit flag indicates that the PHRMAC CE transmission corresponds to a first transmission attempt and asecond value of the one-bit flag indicates that the PHR MAC CEtransmission corresponds to a subsequent transmission attempt.
 9. Theapparatus of claim 6, wherein the timing information comprises anindication of a timing offset between the PHR MAC CE transmission and afirst transmission attempt.
 10. The apparatus of claim 6, wherein thetiming information is transmitted as part of uplink control informationand is encoded separately from the PHR.
 11. A method of a UE configuredfor carrier aggregation using multiple serving cells for power headroomreporting in a mobile communication network, the method comprising:identifying a first transmission occasion for autonomous uplink (“AUL”)transmission on an unlicensed serving cell; generating a power headroomreport (“PHR”) Medium Access Control (“MAC”) control element (“CE”)comprising power headroom information for each activated serving cellconfigured with uplink, wherein the power headroom information for anactivated serving cell is calculated for a predetermined PHR type inresponse to the serving cell being configured with two UL carriers; andtransmitting the PHR MAC CE in an AUL transmission to a radio accessnetwork (“RAN”) node in the mobile communication network.
 12. A UEapparatus configured for carrier aggregation using multiple servingcells for power headroom reporting in a mobile communication network,the apparatus comprising: a processor that: identifies a firsttransmission occasion for autonomous uplink (“AUL”) transmission on anunlicensed serving cell, and generates a power headroom report (“PHR”)Medium Access Control (“MAC”) control element (“CE”) comprising powerheadroom information for each activated serving cell configured withuplink, wherein the power headroom information for an activated servingcell is calculated for a predetermined PHR type in response to theserving cell being configured with two UL carriers; and a transceiverthat transmits the PHR MAC CE in an AUL transmission to a radio accessnetwork (“RAN”) node in the mobile communication network.
 13. A methodof a UE configured with carrier aggregation for power headroom reportingin a mobile communication network, the method comprising: identifying afirst transmission occasion on a configured uplink grant resource;generating a power headroom report (“PHR”) Medium Access Control (“MAC”)control element (“CE”) comprising power headroom information for eachactivated serving cell, wherein the power headroom information iscalculated for a predetermined PHR type in response to a serving cellbeing configured with two UL carriers; and transmitting the PHR MAC CEto a radio access network (“RAN”) node in the mobile communicationnetwork.
 14. The method of claim 13, wherein generating the PHR MAC CEcomprises reporting a virtual power headroom for each activated servingcell in response to the PHR MAC CE being transmitted on a configureduplink grant and further in response to a MAC entity of the UE beingconfigured to deprioritize a lower priority uplink transmission in favorof a higher priority uplink transmission.
 15. The method of claim 14,wherein preparing the PHR MAC CE comprises reporting a virtual PHR for apredefined PHR type in response to a serving cell being configured withtwo UL carriers.
 16. The method of claim 13, wherein the UE isconfigured for carrier aggregation using multiple activated servingcells, wherein preparing the PHR MAC CE comprises reporting an actualPHR for the serving cell on which the PHR MAC CE is to be transmittedand reporting virtual PHR for one or more other activated serving cells.17. A UE apparatus configured with carrier aggregation for powerheadroom reporting in a mobile communication network, the apparatuscomprising: a processor that: identifies a first transmission occasionon a configured uplink grant resource; and generates a power headroomreport (“PHR”) Medium Access Control (“MAC”) control element (“CE”)comprising power headroom information for each activated serving cell,wherein the power headroom information is calculated for a predeterminedPHR type in response to a serving cell being configured with two ULcarriers; and a transceiver that transmits the PHR MAC CE in aconfigured grant transmission to a radio access network (“RAN”) node inthe mobile communication network.
 18. The apparatus of claim 17, whereingenerating the PHR MAC CE comprises reporting a virtual power headroomfor each activated serving cell in response to the PHR MAC CE beingtransmitted on a configured uplink grant and further in response to aMAC entity of the apparatus being configured to deprioritize a lowerpriority uplink transmission in favor of a higher priority uplinktransmission.
 19. The apparatus of claim 18, wherein preparing the PHRMAC CE comprises reporting a virtual PHR for a predefined PHR type inresponse to a serving cell being configured with two UL carriers. 20.The apparatus of claim 17, wherein that apparatus is configured forcarrier aggregation using multiple activated serving cells, whereinpreparing the PHR MAC CE comprises reporting an actual PHR for theserving cell on which the PHR MAC CE is to be transmitted and reportingvirtual PHR for one or more other activated serving cells.